System and method for single-action returns of remotely purchased merchandise

ABSTRACT

A system and method for performing single-action returns of remotely purchased merchandise is provided. The system preferably includes at least one server and at least one client coupled via a network. The server is preferably operable to identify the user of the client system and retrieve a transaction listing for the identified user. The client system preferably displays the transaction listing to the user and allows the user to perform a single action to select transactions and/or merchandise for returns processing. In response to the single action performed, the server system preferably initiates and completes a returns process based upon stored user preferences for such returns. The returns process can include returning merchandise to the retailer from which it was purchased, auctioning the unwanted merchandise, notifying a shipping agent of the return as well as other return procedures.

RELATED PATENT APPLICATION

[0001] This application claims the benefit of U.S. Provisional Application No. 60/191,811, filed Mar. 24, 2000, and entitled “System And Method For Single-Action Returns Of Remotely Purchased Merchandise”.

TECHNICAL FIELD

[0002] The present invention relates in general to electronic commerce transactions and, more particularly, to a method and system for performing single-action returns of remotely purchased items.

BACKGROUND

[0003] The Internet or World Wide Web is especially conducive to conducting electronic commerce. Many Web servers have been developed through which vendors can advertise and sell product. The products can include items (e.g., music) that are delivered electronically to the user over the Internet and items (e.g., books) that are delivered through conventional distribution channels (e.g., a shipping agent). A server computer system may provide an electronic version of a catalog that lists the items that are available. A user may browse through the catalog using a browser and select various items to purchase. When the user has completed selecting items to be purchased, the server computer system then prompts the user for information to complete the ordering of the items. This user-preference profile may include the user's name, the user's credit card number, a shipping address for the order as well as other information. The server computer system then typically confirms the order by sending a confirming web page to the client computer system.

[0004] In addition to security concerns, purchasing items over the Internet has forced many changes in habit for customary brick and mortar shoppers. Internet shoppers are not only no longer able to pick up, try on or otherwise interact with merchandise available for purchase, Internet shoppers are subject to significant changes in the procedures necessary to return an item purchased on-line.

[0005] The ability to simply carry a purchased item back to the retail counter from which it was purchased to request a refund does not typically exist for Internet shoppers. While some brick and mortar stores with Internet counterparts accept the return of merchandise purchased from their Internet counterparts, this is certainly the exception rather than the rule. Therefore, many Internet shoppers are faced with the logistical nightmare of having to return remotely purchased merchandise to a warehouse or returns facility operated by the Internet retailer.

[0006] There exists a myriad of issues with which an Internet customer must contend to return this remotely purchased merchandise. For example, is the item returnable, how will the refund be paid, what shipping agent should be used, how efficient is the long distance returns process, what happens if the package is lost or damaged in transit. These and many other issues are currently contributing to the limited acceptance that Internet commerce has experienced.

SUMMARY

[0007] In accordance with teachings of the present disclosure, a system and method are described for single-action returns of remotely purchased merchandise.

[0008] In one aspect of the present invention, a method for processing merchandise returns is provided. The method preferably includes identifying a user, gathering a transaction history associated with the identified user and displaying the transaction history associated with the identified user. The method may further include initiating a returns process in response to selection, by the user, of a transaction displayed in the transaction history.

[0009] In another aspect of the present invention, a method for processing merchandise returns is provided. The method is preferably operable to display, on a client system, a transaction listing containing transactions associated with a user, the transaction listing preferably including at least one individual transaction indicative of merchandise purchased by the user from a retailer. The method is preferably further operable to initiate a returns process in response to selection of at least one individual transaction by the user.

[0010] In yet another aspect of the present invention, a system for processing merchandise returns is provided. The system preferably includes at least one server communicatively coupled to a network wherein the server is operable to receive single-action requests from the network. Also preferably included in the system is at least one transaction database and at least one customer database communicatively coupled to the server. A program of instructions, executable by the server, is also preferably included. The program of instructions is preferably operable to access a client identifier included in the return request, identify a customer in the customer database based upon the client identifier and create at least one transaction listing from transactions included in the transaction database associated with the identified customer.

[0011] The present invention provides a method and system for single-action returns of remotely purchased merchandise in a client/server environment. The single-action returns capability of the present invention reduces the number of user interactions needed to return an item and reduces the amount of sensitive information that is transmitted between a client system and a server system.

[0012] In one embodiment, the server system preferably assigns a unique client identifier to each client system. The server system may also store user-specific return information to enable the processing of merchandise return transactions by the user. The user-specific information may have been collected from a previous return by the user or by some other method. The server system preferably maps each client identifier to a user that may use that client system to return an item of merchandise. The server system may map the client identifiers to the user who last returned an item using that client system. When a user wants to return an item of merchandise, the user preferably uses a client system to send a return request along with their client identifier to a server system. The server system then preferably determines whether the client identifier for that client system is mapped to a user. If so mapped, the server system determines whether single-action returns is enabled for that user at that client system. If enabled, the requested information is sent (e.g., via a web page) to the client computer system along with an indication of the single action to be performed which will begin the process of returning an item of merchandise.

[0013] When single-action returns are enabled, the user need only perform a single action (e.g., click a mouse button) to process the return of selected item(s). When the user performs that single action, the client system notifies the server system. The server system then preferably completes the merchandise return by adding the user-specific return information for the user that is mapped to that client identifier to the item return information (e.g., product identifier, retailer, credit account, etc.). Also, since the client identifier identifies a user-preference profile preferably stored at the server system, there is no need for sensitive information to be transmitted via the Internet or other communications medium.

[0014] The present invention provides a method and system for returning a remotely purchased item using a client system. The client system is provided with an identifier that identifies a customer. The client system preferably displays information that identifies a user's transaction history and displays an indication of an action (e.g., a single action such as clicking a mouse button) that a user is to perform to return an undesired item of merchandise. In response to the indicated action being performed, the client system preferably sends to a server system the provided identifier and a request to return the identified item or items of merchandise. The server system uses the identifier to identify any additional information needed to process the return of selected item(s) and then completes the return process including managing the shipping of the merchandise and the crediting of a consumer account.

[0015] A server system is preferably employed which receives and stores the additional information for customers using various computer systems so that the server system can process such returns. The server system preferably stores the received additional information associated with an identifier of the customer and provides the identifier to the client system. When requested by the client system, the server system preferably provides information describing the item(s) to the requesting client system. When the server system receives a return request from a client system, the server system combines the additional information stored in association with the identifier included in the return request to effect the return of the item(s).

BRIEF DESCRIPTION OF THE DRAWINGS

[0016] A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:

[0017] FIGS. 1A-1B illustrate web pages incorporating teachings of the present invention;

[0018]FIG. 2 is a block diagram illustrating a system incorporating teachings of the present invention;

[0019]FIG. 3 is a flow diagram of a routine capable of enabling single-action returns according to one embodiment of the present invention;

[0020]FIG. 4 is a flow diagram capable of generating a web page in which single-action returns is enabled according to one embodiment of the present invention;

[0021]FIG. 5 is a flow diagram of a routine capable of processing a single-action return according to one embodiment of the present invention;

[0022] FIGS. 6A-6B illustrate flow diagrams capable of completing the processing of a return request incorporating teachings of the present invention; and

[0023] FIGS. 7A-7C illustrate a user preference profile hierarchical data entry mechanism according to one embodiment of the present invention.

DETAILED DESCRIPTION

[0024] The preferred embodiments of the present invention and its advantages are best understood by referring to the FIGS. 1-7C of the drawings, like numerals being used for like and corresponding parts of the various drawings.

[0025] FIGS. 1A-1B illustrate web pages incorporating teachings of the present invention. Specifically, FIG. 1A illustrates a web browser displaying a web page containing transaction history 101 which includes individual transactions indicative of merchandise purchased by a user logged on to a client system. This example web page was preferably sent from a server system to the client system when the user logged on to the client system and requested to process a merchandise return. This example web page contains transaction listing 101, returns summary section 102, single-action returns section 103, detailed item description section 104, user identification section 107, and returns information section 108. One skilled in the art can appreciate that these various sections may be omitted, rearranged or adapted in various ways without departing from the spirit and scope of the present invention. In general, the user is preferably made aware of the item or items to be returned by the single action and of the single action needed to begin the returns process.

[0026] Transaction listing 101 and detailed item description section 104 preferably provide information that identifies and describes the item(s) selected by the user and which may be returned. The server system adds transaction listing 101 and detailed item description 104 to each web page for the item(s) the user has purchased from various retailers. The server system, however, preferably adds single-action returns section 103 when single-action ordering is enabled for the user logged onto the client system. One skilled in the art would appreciate that a single web page on the server system may contain all these sections but single-action returns section 103 may be selectively included or excluded before sending the web page to the client system.

[0027] Single-action returns section 103 allows the user to specify, with a single action such as a single click of a mouse button, to return items of merchandise selected from individual transactions contained in transactions listing 101. Once the user has performed the preferred single action, the returns process for the selected item(s) is initiated. Single-action returns section 103 preferably contains single-action return button 103 a, user identification subsection 103 b, and single-action return information subsections 103 c and 103 d.

[0028] User identification subsection 103 b preferably displays enough information such that the logged on user can be assured that the server system has correctly recognized them. To reduce the chances of sensitive information being intercepted, the server system preferably sends only enough information to the client system so that the user is confident that the server system has correctly identified the user, yet not enough information to be useful to an unscrupulous interceptor.

[0029] Single-action returns information subsections 103 c and 103 d allow the user to view or edit various settings in their user preference profile for single-action returns or to obtain more information related to the single-action returns functionality. If the user wants to verify accounts to be credited, or other user-specific information, the user can select the “Verify One-Click Settings” link 103 c to view and/or edit their user preference profile. In response to selection of “Verify One-Click Settings” link 103 c, the server system may require the user to perform a “server login” so that the identity of the user can be verified before any confidential information is viewed or modified. The server system then sends a web page to the client system for display and possible modification of the user specific information contained in the user preference profile. In this way, the transmission of sensitive information can be minimized or avoided unless requested by the verified user.

[0030] When the user selects single-action returns button 103 a, the client system sends a return request to the server system indicating the user's desire that the merchandise items associated with transactions selected in transaction listing 101 be returned. After the server system receives the return request, the server system provides the client system with a new web page confirming the receipt of the return request. The processing of the client system and the server system will be discussed in greater detail below.

[0031]FIG. 1B illustrates the display of a web page confirming server system receipt of a single-action return request. The confirmation web page preferably contains essentially the same information as the web page containing transactions listing 101 (i.e., FIG. 1A) except that return request confirmation section 105 is displayed at the top of the web page. Return request confirmation section 105 confirms that the single-action return request has been received and the return request is being processed. The return request confirmation web page also provides link 106 to allow the user to review and change the single-action returns in returns listing 110. In an alternate embodiment, the return request confirmation web page can be identical to the web page containing transaction listing 101, as illustrated in FIG. 1A, except that single-action returns button 103 a is replaced with a message confirming the return request (not expressly illustrated).

[0032] If single-action returns is not currently enabled for the client system but could be enabled, the server system preferably generates a web page similar to that illustrated in FIG. 1A, except that single-action returns button 103 a is replaced by a single-action returns enable button (not expressly illustrated). Such a button preferably contains text instructing the user to click on the button to enable single-action returns. When the user clicks on the button, the server system preferably sends the web page of FIG. 1A to the client system for display. Single-action returns can be enabled whenever the server system has stored sufficient user-specific information in a user preference profile for that user or client system to complete a single-action return. If the server system does not have sufficient information, when the user selects single-action returns button 103 a, or an enable single-action returns button (not expressly shown) the server system preferably provides a web page to collect any additional information necessary. The server system may require the user to “login” so that the identity of the user can be verified before the single-action returns capability is enabled or confidential information is shared.

[0033]FIG. 2 is a block diagram illustrating a system incorporating teachings of the present invention. System 200 preferably supports single-action returns over the Internet using the World Wide Web. Server system 210 includes server engine 211, client identifier/customer table 212, various web page templates 213, customer database 214, transaction database 215, and retailer database 216. Server engine 211 preferably receives HTTP (Hypertext Transfer Protocol) requests to access web pages identified by URLs (Universal Resource Locator) and provides the web pages to the various client systems 220. Such an HTTP request may indicate that the user has performed the single action necessary to effect single-action returns.

[0034] Customer database 214 preferably contains customer information for various users or potential users. Customer information may include user-specific return information such as the name of the customer, credit information, and shipping information in a user preference profile. Transaction database 215 preferably contains entries indicative of transactions associated with registered users, preferably transactions which were performed at single-action returns participating retailers. Retailer database 216 contains a listing of the various retailers that participate in a local returns of remotely purchased merchandise program. Client identifier/customer table 212 contains a mapping from each client identifier, which is a globally unique identifier that uniquely identifies a client system, to the customer last associated with that client system.

[0035] Client system 220 preferably contains browser 221 and assigned client identifier 222. The client identifier 222 is preferably stored in a file as a “cookie.” In one embodiment, server system 210 assigns and sends client identifier 222 to client system 220 when client system 220 first interacts with server system 210. From then on, client system 220 includes its own client system identifier 222 with all messages sent to server system 210 so that server system 210 can identify the source of a communication or return request. Server system 210 and client system 220 interact by exchanging information via communications link 230, which preferably includes transmission over the Internet. Server system 210 may also retrieve transaction information from various retailer databases remotely located, as may be indicated in retailer database 216, with respect to server system 210 via communications link 230.

[0036] One skilled in the art can appreciate that the single-action returns teachings of the present invention can be used in various environments other than the Internet. For example, various communication channels may be used such as a local area network, a wide area network, or a point-to-point dial up connection. Also, server system 210 may comprise any combination of hardware or software capable of processing returns in response to the single action teachings of the present invention. Client system 220 may comprise any combination of hardware or software that can interact with server system 210. Systems 210 and 220 may include television-based systems or various other consumer products capable of electronic commerce transactions.

[0037]FIG. 3 is a flow diagram of a routine capable of enabling single-action returns for a user according to one embodiment of the present invention. To enable single-action returns, server system 210 preferably has information about the user contained in a user preference profile that is stored in customer database 214. Server system 210 can obtain this information in various ways. First, server system 210 can ask the user if they would like to have single-action returns enabled. If so, server system 210 could then prompt the user using a web page to obtain user-specific return information for inclusion in a user preference profile. Second, server system 210 could save the user-specific return information collected during a first return request processing. Server system 210 could then, either automatically or with the user's consent, enable single-action returns.

[0038] In step 301, server system 210 retrieves client identifier 222 preferably included in a message sent by client system 220. In step 302, server system 210 updates client identifier/customer table 212 to indicate that client identifier 222 has been associated with that user. In step 303, server system 210 preferably sets a flag indicating that single-action returns is enabled for client identifier 222 and the user currently using client system 220. The flag may be stored in the client identifier/customer table 212. In step 304, server system 210 supplies a confirming web page, as illustrated in FIG. 1B, to client system 220 for display. The next time a user wishes to return an item of merchandise, client system 220 will supply its client identifier 222 to server system 210. If single-action returns is enabled for that user, server system 210 preferably assumes that the user at client system 220 is the customer associated with that client identifier 222 in the client identifier/customer table 212. Thus, for security reasons, a user may not want to allow server system 210 to enable single-action returns if there is a possibility that someone else may use that same client system 220. An alternative to automatically enabling single-action returns is to have the user log on to server system 210.

[0039]FIG. 4 is a flow diagram of a routine capable of generating a web page in which single-action returns is enabled according to one embodiment of the present invention. When single-action returns is enabled, server system 210 preferably generates a web page, similar to that illustrated in FIG. 1A, including single-action returns section 103 as indicated at step 401. In one embodiment, server system 210 adds partial user-specific return information 103 b from the user preference profile to the web page displayed. Information displayed may include the customer's name, the last four digits of a credit card number, or a nickname selected by the user. Such information is preferably kept to the minimum amount of information necessary to indicate to the user whether or not server system 210 is using the correct user preference profile. In step 402, if the single-action returns flag has been set for client identifier 222 and customer combination, then server system 210 continues at step 403, else server system 210 completes. In step 403, server system 210 adds single-action returns section 103 to the web page displayed and completes.

[0040]FIG. 5 is a flow diagram of a routine capable of processing single-action returns according to one embodiment of the present invention. In one embodiment of the present invention, the method of FIG. 3 can be implemented within the method of FIG. 5.

[0041] Method 500 of FIG. 5 begins at step 505. Once initialized, method 500 proceeds to step 510. At step 510, the user of client system 220 is identified. One method of identifying the user of client system 220 is the method of FIG. 3. An alternative method of identifying the user of client system 220 is to obtain and review client identifier 222, if one is present, on client system 220. If the user of the client system is a new user, i.e., not yet registered or no client identifier 222 is provided, method 500 proceeds to step 515.

[0042] At step 515, it is determined whether or not the user is to be registered. This determination can be made by prompting the user, or by other means. If the new user does not wish to be registered for single-action returns services or it is determined that the user is not to be registered, method 500 proceeds to step 520 where method 500 is ended. If the new user wishes to enable single-action returns, method 500 proceeds to step 525.

[0043] At step 525, a user preference profile for the new user is created and stored preferably on server system 210. Once the new user is registered and the user preference profile stored, a client identifier 222 is deposited on client system 220 and method 500 proceeds to step 535.

[0044] If at step 510, the user on client system 220 is identified as a registered user, i.e., a client identifier 222 exists on client system 220, method 500 proceeds to step 530. At step 530, the user preference profile of the registered user is retrieved and mapped using customer database 214 and client ID/customer table 212. Once the user preference profile has been retrieved, such as at step 530, or created, such as at step 525, method 500 proceeds to step 535.

[0045] At step 535, a transaction history for the user is preferably retrieved from transactions database 215. Transactions database 215 is preferably maintained by server system 210. However, transactions database 215 can be maintained at another location as well as created real-time from a collection of databases located at member retail sites, credit card sites or other data bases. Once an appropriate transaction history for the registered user has been retrieved at step 535, method 500 proceeds to step 540.

[0046] At step 540, the transaction history retrieved at step 535 is preferably displayed to the user for their perusal and subsequent selection of items of merchandise to be returned. The transaction history is preferably displayed in a manner similar to that illustrated in FIG. 1A. In addition to the transaction history, single-action returns section 103 of the present invention is also preferably included on the displayed web page. Once transaction history 101 and other desired components of a single-action returns web page are displayed, method 500 proceeds to step 545.

[0047] At step 545, method 500 waits or loops until the user selects a transaction or item to be processed for returns. If a transaction or item is not selected within a predetermined amount of time, method 500 proceeds to step 550 where method 500 ends. Method 500 is designed to end after a predetermined amount of time for security reasons which can arise from client system 220 being left unattended or for other computer security threats. In response to the selection of an item to be returned and the subsequent selection of single-action returns button 103 a at step 545, method 500 proceeds to step 555. At step 555, the processing necessary for the return of the selected item or items of merchandise is initiated.

[0048] Referring now to FIG. 6A, one embodiment of a flow diagram capable of completing the processing of a return request incorporating teachings of the present invention is shown. As illustrated in the embodiment of FIG. 6A, in response to the initiation of returns processing at step 555, method 500 a proceeds to step 558.

[0049] At step 558, the selected item or transaction is evaluated to determine whether or not the return is a valid return. One method of validating a return might involve comparing the item to be returned against a returns rule set for the retailer from which the item was purchased. Alternatively, if the transaction represented the purchase of a perishable item, a return might be determined to not be valid. If it is determined that the selected transaction or item is not a valid return, method 500 a proceeds to step 561.

[0050] At step 561, the user is notified of the invalid return such as by a web page, email, or other capable means. Once the user has been notified that the return is invalid at step 561, method 500 a ends at step 564. As an alternative to ending at any end step of methods 500, 500 a or 500 b, methods 500, 500 a or 500 b can return to a previous step, such as step 540 where the transaction listing is displayed to the user, or perform other actions within the spirit and scope of the present invention.

[0051] If at step 558, it is determined that the selected item or transaction for return is valid, method 500 a proceeds to step 567. At step 567, the retailer from which the item was purchased is notified of the pending merchandise return. After the appropriate retailer is notified at step 567, the transaction information and the necessary user specific information such as that contained in the user preference profile, is provided to the retailer at step 570.

[0052] In addition to providing the retailer the necessary transaction information and the necessary user specific information at step 570, a shipping agent is notified of the need for a package pick up such that the item selected by the user may be returned at Step 573. To further simplify processing for both the shipping agent and the user, a return shipping label is preferably produced for the user to place on the package in which the merchandise for return will be shipped back to the retailer at step 576. It is also possible to have shipping paperwork generated and printed out at the facility of the shipping agent. At step 579, the package, once picked up by the shipping agent, is forwarded to the appropriate destination, such as a retailer depot, auction site, etc. Method 500 a completes returns processing at step 582.

[0053] Referring now to FIG. 6B, an alternate embodiment of a flow diagram capable of completing the processing of a single-action return request incorporating teachings of the present invention is shown. Similar to FIG. 6A, in response to the initiation of returns processing at step 555, method 500 b proceeds to step 558.

[0054] At step 558, the selected item or transaction is evaluated to determine whether or not the return is a valid return. One method of validating a return might be to compare the item to be returned against a returns rule set for the retailer from which the item was purchased. Alternatively, if the transaction represented the purchase of a perishable item, a return might be determined to not be valid. If it is determined that the selected transaction or item is not a valid return, method 500 b proceeds to step 561.

[0055] At step 561, the user is notified of the invalid return. Once the user has been notified that the return is invalid at step 561, method 500 b ends at step 564.

[0056] If at step 558, it is determined that the selected item or transaction for return is valid, method 500 b proceeds to step 573. At step 573, a shipping agent is notified of a package pick up for the return of the item selected by the user. To further simplify processing for both the shipping agent and the user, a return shipping label is preferably produced for the user to place on the package in which the return will be shipped at step 576. At step 579, the package, once picked up by the shipping agent, is forwarded to its appropriate destination.

[0057] Once the merchandise to be returned has been received at its destination or while the merchandise is in transit, the merchandise is disposed of at step 585. The present invention envisions a variety of different methods by which the returned merchandise may be disposed of. For example, the merchandise may be auctioned on an auctioning web-site, a live auction may be employed to dispose of the returned merchandise, or as illustrated in FIG. 6A, the merchandise may be returned to the retailer from which it was purchased.

[0058] Once the merchandise has been disposed of at step 585, the proceeds of the disposal are credited to the user based upon settings available in the user preference profile at step 588. This method of disposal allows an auctioning agent to obtain the best price for the returned merchandise and to collect a commission for their role in the disposition of the merchandise should they desire. For products which get returned to the retailer from which they were purchased, the user may be able to obtain a full refund for the unwanted merchandise from the retailer. Other methods of merchandise disposal are considered within the spirit and scope of the present invention. Once the user has been appropriately credited, method 500 b completes at step 591.

[0059] To help minimize shipping costs and user confusion, the server system may combine various single-action returns into a multiple-item return. For example, if a user wishes to return more than one item to any given retailer or central depot, those returns may be cost effectively combined into a single return for shipping. As such, the server system preferably combines the single-action returns when their destination addresses are the same.

[0060] FIGS. 7A-7C illustrate a hierarchical data entry mechanism in one embodiment. When collecting information from a user such as for a user preference profile, a web page typically consists of a long series of data entry fields that may not all fit onto the display at the same time. Thus, a user needs to scroll through the web page to enter the information. When the data entry fields do not fit onto the display at the same time, it is often difficult for the user to get an overall understanding of the type and organization of the data to be entered. The hierarchical data entry mechanism allows a user to understand the overall organization of the data to be entered even though the all data entry fields would not fit onto the display at the same time.

[0061]FIG. 7A illustrates an outline format of a sample form to be filled in. The sample form contains various sections identified by letters A, B, C, and D. When the user selects start button 701, section A 702 expands to include the data entry fields 703 a-g illustrated if FIG. 6B for the user preference profile information.

[0062]FIG. 7B illustrates the expansion of section A 702. Since only section A 702 has been expanded, the user can view the data entry fields 703 a-g of section A 702 and summary information associated with sections B, C, and D at the same time. The user then enters data in the various data entry fields 703 a-g that are displayed. Upon completion, the user selects either next button 704 or previous button 705. Next button 704 causes section A 702 to be collapsed and section B 706 to be expanded so that financial information may be entered.

[0063]FIG. 7C illustrates the expansion of section B 706. If previous button 705 had been selected, section A 702 would have collapsed as shown in FIG. 7A. This collapsing and expanding can be repeated for each section. At any time during the data entry process, if an error is detected, a web page is preferably generated with the error message in close proximity to the data entry field 703 a-g that contains the error. This web page is then displayed by client system 220 to inform the user of the error. In addition, each of the data “entry” fields may not be editable until the user clicks on the data entry field 703 a-g or selects an edit button (not expressly shown) associated with the data entry field. In this way, the user is prevented from inadvertently changing the contents of a data entry field 703 a-g. When the user clicks on a data entry field 703 a-g, a new web page may be presented to the user that allows for the editing of the data associated with the field. When editing is complete, the edited data is preferably displayed in data entry field 703 a-g. Also, the form is more compact because the various data entry options (e.g., radio button) are displayed only on the new web page when the field is to be edited.

[0064] Although the present invention has been described in terms of various embodiments, it is not intended that the invention be limited to these embodiments. Modification within the spirit of the invention will be apparent to those skilled in the art. For example, server system 210 may map client identifier 222 to multiple customers who have recently used client system 220. Server system 210 can then allow the user to identify themselves by selecting one of the mappings based preferably on a display of partial user-specific order information. Also, various different single actions can be used to effect the return of an item. For example, a voice command may be spoken by the user, a key may be depressed by the user, a button on a television remote control device may be depressed by the user, or selection using any pointing device may be effected by the user. Although a single action may be preceded by multiple physical movements of the user (e.g., moving a mouse and clicking selected items or transactions for return), the single action generally refers to a single event received by client system 220 that indicates the desire to return any selected items or transactions. Finally, the user can be alternately identified by a unique customer identifier 222 that is provided by the customer when the customer initiates access to server system 210 and sent to server system 210 with each message. Customer identifier 222 could be also stored persistently on client system 220 so that the user does not need to re-enter their customer identifier 222 each time access is initiated.

[0065] Although the present invention has been described in detail, it should be understood that various changes, substitutions and alterations can be made thereto without departing from the spirit and scope of the invention. 

What is claimed is:
 1. A method for processing the returns of merchandise purchased through the World Wide Web comprising: identifying a user; gathering a transaction history associated with the identified user; displaying the transaction history associated with the identified user; and initiating a returns process in response to selection, by the user, of a transaction displayed in the transaction history.
 2. The method of claim 1 further comprising retrieving a preference profile for the identified user.
 3. The method of claim 2 further comprising crediting a user account indicated in the user preference profile based upon the transaction selected.
 4. The method of claim 1 further comprising notifying a retailer associated with the transaction selected by the user.
 5. The method of claim 4 further comprising providing the retailer with the transaction information and user information associated with the transaction selected by the user.
 6. The method of claim 1 further comprising generating a return shipping label for the merchandise to be returned.
 7. The method of claim 1 further comprising notifying a shipping provider of a merchandise return to be picked up.
 8. The method of claim 1 further comprising auctioning the merchandise selected for return by the user.
 9. The method of claim 1 further comprising communicating between a client system and a server system via the Internet.
 10. A method for processing the local return of remotely purchased merchandise comprising: displaying, on a client system, a transaction listing containing transactions associated with a user; the transaction listing including at least one individual transaction indicative of merchandise purchased by the user from a retailer; and initiating a returns process in response to selection of at least one individual transaction by the user.
 11. The method of claim 10 further comprising: identifying the user; and retrieving transaction information associated with the identified user.
 12. The method of claim 10 further comprising: transmitting an identifier to a server system; and retrieving a user preference profile previously stored for the user identified by the identifier.
 13. The method of claim 12 further comprising: completing the returns process based upon settings in the user preference profile.
 14. The method of claim 10 further comprising: notifying the retailer of the merchandise to be returned; and providing transaction information associated with the merchandise return the retailer.
 15. The method of claim 10 further comprising: notifying a shipping agent of a merchandise return package to be shipped; and generating a shipping label for the merchandise return package.
 16. The method of claim 12 further comprising issuing a credit to a user account indicated in the user preference profile.
 17. A system for processing merchandise returns comprising: a server communicatively coupled to a network; the server operable to receive single-action requests from the network; at least one transaction database communicatively coupled to the server; at least one customer database communicatively coupled to the server; a program of instructions executable by the server; and the program of instructions operable to access a client identifier included in the return request, identify a customer in the customer database based upon the client identifier and create at least one transaction listing from transactions included in the transaction database associated with the identified customer.
 18. The system of claim 17 further comprising: at least one client communicatively coupled to the network; at least one display operably coupled to the client; the display operable to display the transaction listing created by the server; and the client operable to transmit a single-action return request to the network in response to selection of at least one transaction displayed in the transaction listing.
 19. The system of claim 17 further comprising the program of instructions operable to initiate a returns process in response to selection of at least one transaction from the transaction listing.
 20. The system of claim 19 further comprising the program of instructions operable to retrieve a preference profile for the identified user and complete the returns process based upon settings included in the preference profile. 